Throttle
Dependency Breakers
Restrict acceptable dependencies with work-in-progress limits.
Dependency Breakers: Attend • Automate • Block • Contain • Coordinate • Decouple • Flag • Formalize • Measure • Prioritize • Redesign • Reteam • Rotate • Self-service • Standardize • Swarm • Throttle • Toggle • Visualize • Volunteer
Purpose
To maintain control over your workflow, restrict the acceptance of dependencies by implementing work-in-progress (WIP) limits. This prevents your team from being overwhelmed and minimizes downstream impacts. By avoiding overloading your teams with excessive work, you simultaneously decrease the number and variety of dependencies they need to tackle. It is a proactive strategy that enhances efficiency and minimizes the adverse effects of dependencies on your projects.
Notes
Dependencies are not necessarily bad. Actually, there are many good reasons for people to depend on each other. But you have a problem when those dependencies result in value that is not able to flow.
Rules / Constraints
We have not yet defined any rules or constraints.
“We have broken the cycle of dependency. People have found out they're better off working.”
(Source: John Engler)